The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
docs	Ready	Preview, Comment	Jan 10, 2026 7:12pm

Greptile Overview

Greptile Summary

This PR attempts to fix router edge deletion and improve router prompting, but introduces a critical bug in route ID generation that will break workflow execution.

What Changed

The PR makes 4 main changes to the router v2 block:

1. Edge deletion fix (condition-input.tsx): Now properly removes edges when deleting router routes using the router-${id} handle prefix
2. Route ID fallback fix (workflow-block.tsx): Corrected fallback route ID from route-route1 to route1
3. Autoconnect support (workflow.tsx): Added router_v2 to autoconnect logic to automatically connect new blocks
4. Prompt improvements (router.ts): Made the system prompt more forceful to ensure LLM always returns a route ID
5. Fallback behavior (router-handler.ts): Added fallback to first route instead of throwing error when LLM returns invalid route ID

Critical Issue Found

Route ID generation inconsistency in condition-input.tsx (line 627-632):

• Default route uses: generateStableId(blockId, 'route1') → produces blockId-route1
• New routes use: generateStableId(blockId, 'route-${Date.now()}') → produces blockId-route-1234567890
• Expected format: blockId-route2, blockId-route3, etc.

This breaks the entire routing system because:

• Handles are created with these IDs: router-${route.id}
• Executor looks for handles matching router-${chosenRoute.id}
• Mismatched formats mean connections won't be found and workflow execution will fail

Additional Concern

The silent fallback in router-handler.ts masks routing failures. While it prevents crashes, users won't know when the router isn't working properly, making debugging difficult.

Recommendation

DO NOT MERGE until the route ID generation bug is fixed. The edge deletion and autoconnect fixes are good, but the ID generation issue will cause runtime failures.

Confidence Score: 1/5

• This PR contains a critical bug that will break router workflow execution
• Score of 1 reflects the critical route ID generation bug in condition-input.tsx that creates inconsistent ID formats. This will cause edge matching failures and break workflow execution. While other changes are correct, this single issue makes the PR unsafe to merge.
• Pay immediate attention to condition-input.tsx line 627 - the route ID generation must be fixed before merging

Important Files Changed

File Analysis

Sequence Diagram

sequenceDiagram
    participant User
    participant ConditionInput
    participant WorkflowBlock
    participant WorkflowCanvas
    participant RouterHandler
    participant EdgeManager

    Note over User,EdgeManager: Router Port Creation & Connection Flow

    User->>ConditionInput: Add new route
    ConditionInput->>ConditionInput: Generate route ID (BUG: uses timestamp)
    ConditionInput->>ConditionInput: Save route with ID "blockId-route-123456789"
    
    WorkflowBlock->>WorkflowBlock: Parse routes from JSON
    WorkflowBlock->>WorkflowBlock: Create handle with id="router-blockId-route-123456789"
    
    User->>WorkflowCanvas: Drag connection from router port
    WorkflowCanvas->>WorkflowCanvas: Auto-detect router handle
    WorkflowCanvas->>WorkflowCanvas: Create edge with sourceHandle="router-blockId-route-123456789"
    
    Note over User,EdgeManager: Workflow Execution Flow
    
    User->>RouterHandler: Execute workflow
    RouterHandler->>RouterHandler: Call LLM with context + route descriptions
    RouterHandler->>RouterHandler: LLM returns route ID
    
    alt Valid route ID
        RouterHandler->>RouterHandler: Find route in parsed routes
        RouterHandler->>EdgeManager: Look for edge with sourceHandle="router-{routeId}"
        EdgeManager->>EdgeManager: Match handle prefix "router-"
        EdgeManager->>RouterHandler: Return target block
        RouterHandler->>RouterHandler: Execute target block
    else Invalid route ID (NEW)
        RouterHandler->>RouterHandler: Log warning
        RouterHandler->>RouterHandler: Fallback to routes[0]
        Note right of RouterHandler: Silent failure - masks issues
        RouterHandler->>EdgeManager: Use first route ID
    end
    
    Note over User,EdgeManager: Edge Deletion Flow (FIXED)
    
    User->>ConditionInput: Delete route
    ConditionInput->>ConditionInput: Get route ID
    ConditionInput->>ConditionInput: Build handlePrefix "router-{routeId}"
    ConditionInput->>WorkflowCanvas: Remove edges matching prefix
    WorkflowCanvas->>WorkflowCanvas: Delete connected edges